docs: Models > Records — Reporting, Monitoring, Attestation#1359
Conversation
jamadriz
left a comment
There was a problem hiding this comment.
refer to comments, other minor general:
"The PR updates visualization dataset names to Inventory Records and Artifact - Limitations, but configure-analytics-exports.qmd (Integrations) still lists Inventory Models and Artifact - Model Limitation. Fine for this PR given stated scope, but users cross-referencing reporting vs integrations may notice. Track for the follow-on story."
Yes, this is covered in the Integrations work outside of the scope of this Story; can you approve so I can wrap this into the release notes deploy? 🙏🏻 |
PR SummaryThis pull request updates the documentation and training materials to reflect a shift in terminology from "model" to "record". The changes impact several guides including attestation, monitoring, reporting, workflows, and AI governance. Key modifications include:
Overall, the PR is focused on clarifying and harmonizing the language used across the documentation by making sure that textual references align with the updated product concepts. These changes do not impact any functional business logic or code execution. Test Suggestions
|
Validate docs site✓ INFO: A live preview of the docs site is available — Open the preview |
* Merge pull request #1359 from validmind/beck/sc-15995/documentation-primary-record-types-phase docs: Models > Records — Reporting, Monitoring, Attestation * Preview for 26.06 release notes + `make get-source` (#1353) * Add temporary release-notes branch ref for 26.06 preview Points to nrichers/sc-16263/release-notes-for-26-06 branch in release-notes repo. * Run make get-source * Add subtitle to all-releases page listing * refreshing vm-library * cache invalidation * Update .github/workflows/validate-docs-site.yaml Co-authored-by: Nik Richers <nik@validmind.ai> * REF FOR PREVIEW, REMOVE BEFORE MERGE * Update .github/workflows/validate-docs-site.yaml --------- Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com> --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Nik Richers <nrichers@gmail.com>
Pull Request Description
What and why?
Important
THIS PR IS NOT EXHAUSTIVE DUE TO THE LARGE SCOPE OF WORK. Refer to "What needs special review?" for follow-on updates.
How to test
Click on the live previews and verify everything looks OK:
Reporting
Monitoring
Attestation
Training — Adminstrator Fundamentals
What needs special review?
Still one more update that needs to be made to the docs as this new functionality is pretty all-encompassing.
What's not covered and will be in a future Story (not using the sc link so the GitHub integration doesn't think these Stories are under review due to this PR being linked):
Dependencies, breaking changes, and deployment notes
n/a
Release notes
n/a
Checklist